A flaw was found in GLib, which is vulnerable to an integer overflow in the g_string_insert_unichar() function. When the position at which to insert the character is large, the position will overflow, leading to a buffer underwrite.

---

• glib2.0 2.84.1-3 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104930)
  [bookworm] - glib2.0 (Minor issue)
  [bullseye] - glib2.0 (Minor issue, fix along with next update)
  https://gitlab.gnome.org/GNOME/glib/-/issues/3677
  https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4588
  https://gitlab.gnome.org/GNOME/glib/-/merge_requests/4592

GLib 2.31.8 and earlier, when the g_str_hash function is used, computes hash values without restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted input to an application that maintains a hash table. NOTE: this issue may be disputed by the vendor; the existence of the g_str_hash function is not a vulnerability in the library, because callers of g_hash_table_new and g_hash_table_new_full can specify an arbitrary hash function that is appropriate for the application.

---

• glib2.0 (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655044)

An issue was discovered in systemd 253. An attacker can modify the contents of past events in a sealed log file and then adjust the file such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."

---

• systemd (unimportant)
  Disputed by upstream
  https://github.com/kastel-security/Journald/blob/main/journald-publication.pdf

An issue was discovered in systemd 253. An attacker can truncate a sealed log file and then resume log sealing such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."

---

• systemd (unimportant)
  Disputed by upstream
  https://github.com/kastel-security/Journald/blob/main/journald-publication.pdf

An issue was discovered in systemd 253. An attacker can modify a sealed log file such that, in some views, not all existing and sealed log messages are displayed. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."

---

• systemd (unimportant)
  Disputed by upstream
  https://github.com/kastel-security/Journald/blob/main/journald-publication.pdf

systemd, when updating file permissions, allows local users to change the permissions and SELinux security contexts for arbitrary files via a symlink attack on unspecified files.

---

• systemd (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725357)
  [wheezy] - systemd (/etc/tmpfiles.d not supported in Wheezy)
  https://bugzilla.redhat.com/show_bug.cgi?id=859060
  only relevant to systems running systemd along with selinux

libldap in certain third-party OpenLDAP packages has a certificate-validation flaw when the third-party package is asserting RFC6125 support. It considers CN even when there is a non-matching subjectAltName (SAN). This is fixed in, for example, openldap-2.4.46-10.el8 in Red Hat Enterprise Linux.

---

• openldap (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965184)
  https://bugs.openldap.org/show_bug.cgi?id=9266
  https://bugzilla.redhat.com/show_bug.cgi?id=1740070
  RedHat/CentOS applied patch: https://git.centos.org/rpms/openldap/raw/67459960064be9d226d57c5f82aaba0929876813/f/SOURCES/openldap-tlso-dont-check-cn-when-bad-san.patch
  OpenLDAP upstream did dispute the issue as beeing valid, as the current libldap
  behaviour does conform with RFC4513. RFC6125 does not superseed the rules for
  verifying service identity provided in specifications for existing application
  protocols published prior to RFC6125, like RFC4513 for LDAP.

contrib/slapd-modules/nops/nops.c in OpenLDAP through 2.4.45, when both the nops module and the memberof overlay are enabled, attempts to free a buffer that was allocated on the stack, which allows remote attackers to cause a denial of service (slapd crash) via a member MODDN operation.

---

• openldap (unimportant)
  http://www.openldap.org/its/index.cgi/Incoming?id=8759
  nops slapd-module not built

slapd in OpenLDAP 2.4.45 and earlier creates a PID file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for PID file modification before a root script executes a "kill cat /pathname" command, as demonstrated by openldap-initscript.

---

• openldap (unimportant)
  http://www.openldap.org/its/index.cgi?findid=8703
  Negligible security impact, but filed #877512

The nss_parse_ciphers function in libraries/libldap/tls_m.c in OpenLDAP does not properly parse OpenSSL-style multi-keyword mode cipher strings, which might cause a weaker than intended cipher to be used and allow remote attackers to have unspecified impact via unknown vectors.

---

• openldap (unimportant)
  Debian builds with GNUTLS, not NSS

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/lib/gssapi/krb5/k5sealv3.c.

---

• krb5 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098754; unimportant)
  https://github.com/LuMingYinDetect/krb5_defects/blob/main/krb5_detect_2.md
  Fixed by: krb5/krb5@c5f9c81
  Codepath cannot be triggered via API calls, negligible security impact
  https://mailman.mit.edu/pipermail/kerberos/2024-March/023095.html

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak in /krb5/src/lib/rpc/pmap_rmt.c.

---

• krb5 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098754; unimportant)
  https://github.com/LuMingYinDetect/krb5_defects/blob/main/krb5_detect_1.md
  Fixed by: krb5/krb5@c5f9c81
  Unused codepath, negligible security impact
  https://mailman.mit.edu/pipermail/kerberos/2024-March/023095.html

An issue was discovered in MIT Kerberos 5 (aka krb5) through 1.16. There is a variable "dbentry->n_key_data" in kadmin/dbutil/dump.c that can store 16-bit data but unknowingly the developer has assigned a "u4" variable to it, which is for 32-bit data. An attacker can use this vulnerability to affect other artifacts of the database as we know that a Kerberos database dump file contains trusted data.

---

• krb5 (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889684)
  https://github.com/poojamnit/Kerberos-V5-1.16-Vulnerabilities/tree/master/Integer%20Overflow
  non-issue, codepath is only run on trusted input, potential integer
  overflow is non-issue

Issue summary: Use of -addreject option with the openssl x509 application adds a trusted use instead of a rejected use for a certificate. Impact summary: If a user intends to make a trusted certificate rejected for a particular use it will be instead marked as trusted for that use. A copy & paste error during minor refactoring of the code introduced this issue in the OpenSSL 3.5 version. If, for example, a trusted CA certificate should be trusted only for the purpose of authenticating TLS servers but not for CMS signature verification and the CMS signature verification is intended to be marked as rejected with the -addreject option, the resulting CA certificate will be trusted for CMS signature verification purpose instead. Only users which use the trusted certificate format who use the openssl x509 command line application to add rejected uses are affected by this issue. The issues affecting only the command line application are considered to be Low severity. The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 3.4, 3.3, 3.2, 3.1, 3.0, 1.1.1 and 1.0.2 are also not affected by this issue.

---

• openssl (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106322)
  [bookworm] - openssl (Only affects 3.5.x)
  [bullseye] - openssl (Only affects 3.5.x)
  https://openssl-library.org/news/secadv/20250522.txt
  openssl/openssl@0eb9acc (master)
  openssl/openssl@e96d224 (openssl-3.5)

OpenSSL 0.9.8i on the Gaisler Research LEON3 SoC on the Xilinx Virtex-II Pro FPGA uses a Fixed Width Exponentiation (FWE) algorithm for certain signature calculations, and does not verify the signature before providing it to a caller, which makes it easier for physically proximate attackers to determine the private key via a modified supply voltage for the microprocessor, related to a "fault-based attack."

---

http://www.eecs.umich.edu/~valeria/research/publications/DATE10RSA.pdf
openssl/openssl#24540
Fault injection based attacks are not within OpenSSLs threat model according
to the security policy: https://www.openssl.org/policies/general/security-policy.html

shadow-utils (aka shadow) 4.4 through 4.17.0 establishes a default /etc/subuid behavior (e.g., uid 100000 through 165535 for the first user account) that can realistically conflict with the uids of users defined on locally administered networks, potentially leading to account takeover, e.g., by leveraging newuidmap for access to an NFS home directory (or same-host resources in the case of remote logins by these local network users). NOTE: it may also be argued that system administrators should not have assigned uids, within local networks, that are within the range that can occur in /etc/subuid.

---

• shadow (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103832)
  [bookworm] - shadow (Minor issue)
  [bullseye] - shadow (Minor issue, disputed, no upstream patch)
  Default subordinate ID configuration in /etc/login.defs could lead to compromise shadow-maint/shadow#1157

initscripts in rPath Linux 1 sets insecure permissions for the /var/log/btmp file, which allows local users to obtain sensitive information regarding authentication attempts. NOTE: because sshd detects the insecure permissions and does not log certain events, this also prevents sshd from logging failed authentication attempts by remote attackers.

---

• shadow (unimportant)
  See #290803, on Debian LOG_UNKFAIL_ENAB in login.defs is set to no so
  unknown usernames are not recorded on login failures

A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.

---

• libgcrypt20 (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065683)
  https://bugzilla.redhat.com/show_bug.cgi?id=2268268
  https://lists.gnupg.org/pipermail/gcrypt-devel/2024-March/005607.html
  https://github.com/tomato42/marvin-toolkit/tree/master/example/libgcrypt
  https://people.redhat.com/~hkario/marvin/
  https://dev.gnupg.org/T7136
  https://gitlab.com/redhat-crypto/libgcrypt/libgcrypt-mirror/-/merge_requests/17
  Not in scope for libgcrypt security policy, work ongoing to add support in the protocol layer

cipher/elgamal.c in Libgcrypt through 1.8.2, when used to encrypt messages directly, improperly encodes plaintexts, which allows attackers to obtain sensitive information by reading ciphertext data (i.e., it does not have semantic security in face of a ciphertext-only attack). The Decisional Diffie-Hellman (DDH) assumption does not hold for Libgcrypt's ElGamal implementation.

---

• libgcrypt20 (unimportant)
• libgcrypt11 (unimportant)
• gnupg1 (unimportant)
• gnupg (unimportant)
  https://github.com/weikengchen/attack-on-libgcrypt-elgamal
  https://github.com/weikengchen/attack-on-libgcrypt-elgamal/wiki
  https://lists.gnupg.org/pipermail/gcrypt-devel/2018-February/004394.html
  GnuPG uses ElGamal in hybrid mode only.
  This is not a vulnerability in libgcrypt, but in an application using
  it in an insecure manner, see also
  https://lists.gnupg.org/pipermail/gcrypt-devel/2018-February/004401.html

_is_safe in the File::Temp module for Perl does not properly handle symlinks.

---

• perl (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776268)
  http://thread.gmane.org/gmane.comp.security.oss.general/6174/focus=6177
  File:Temp::_is_safe() allows unsafe traversal of symlinks [rt.cpan.org #69106] Perl-Toolchain-Gang/File-Temp#14

• perl (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098226)
  [bookworm] - perl (Minor issue; decide for DSA or no-DSA once upstream lands a fix)
  [bullseye] - perl (Minor issue, revisit when fixed upstream)
  Thread creation while a directory handle is open does a fchdir, affecting other threads (race condition) Perl/perl5#23010

A flaw was found in the util-linux chfn and chsh utilities when compiled with Readline support. The Readline library uses an "INPUTRC" environment variable to get a path to the library config file. When the library cannot parse the specified file, it prints an error message containing data from the file. This flaw allows an unprivileged user to read root-owned files, potentially leading to privilege escalation. This flaw affects util-linux versions prior to 2.37.4.

---

• util-linux (unimportant)
  https://bugzilla.redhat.com/show_bug.cgi?id=2053151
  https://lore.kernel.org/util-linux/[email protected]/T/#u
  util-linux/util-linux@faa5a3a
  util-linux in Debian does build with readline support but chfn and chsh are provided
  by src:shadow and util-linux is configured with --disable-chfn-chsh

The SSL protocol, as used in certain configurations in Microsoft Windows and Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Opera, and other products, encrypts data by using CBC mode with chained initialization vectors, which allows man-in-the-middle attackers to obtain plaintext HTTP headers via a blockwise chosen-boundary attack (BCBA) on an HTTPS session, in conjunction with JavaScript code that uses (1) the HTML5 WebSocket API, (2) the Java URLConnection API, or (3) the Silverlight WebClient API, aka a "BEAST" attack.

---

• sun-java6 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645881)
  [lenny] - sun-java6 (Non-free not supported)
  [squeeze] - sun-java6 (Non-free not supported)
• openjdk-6 6b23~pre11-1
• openjdk-7 7~b147-2.0-1
• iceweasel (Vulnerable code not present)
  http://blog.mozilla.com/security/2011/09/27/attack-against-tls-protected-communications/
• chromium-browser 15.0.874.106~r107270-1
  [squeeze] - chromium-browser
• lighttpd 1.4.30-1
  strictly speaking this is no lighttpd issue, but lighttpd adds a workaround
• curl 7.24.0-1
  http://curl.haxx.se/docs/adv_20120124B.html
• python2.6 2.6.8-0.1 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684511)
  [squeeze] - python2.6 (Minor issue)
• python2.7 2.7.3~rc1-1
• python3.1 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678998)
  [squeeze] - python3.1 (Minor issue)
• python3.2 3.2.3~rc1-1
  http://bugs.python.org/issue13885
  python3.1 is fixed starting 3.1.5
• cyassl
• gnutls26 (unimportant)
• gnutls28 (unimportant)
  No mitigation for gnutls, it is recommended to use TLS 1.1 or 1.2 which is supported since 2.0.0
• haskell-tls (unimportant)
  No mitigation for haskell-tls, it is recommended to use TLS 1.1, which is supported since 0.2
• matrixssl (low)
  [squeeze] - matrixssl (Minor issue)
  [wheezy] - matrixssl (Minor issue)
  matrixssl fix this upstream in 3.2.2
• bouncycastle 1.49+dfsg-1
  [squeeze] - bouncycastle (Minor issue)
  [wheezy] - bouncycastle (Minor issue)
  No mitigation for bouncycastle, it is recommended to use TLS 1.1, which is supported since 1.4.9
• nss 3.13.1.with.ckbi.1.88-1
  https://bugzilla.mozilla.org/show_bug.cgi?id=665814
  https://hg.mozilla.org/projects/nss/rev/7f7446fcc7ab
• polarssl (unimportant)
  No mitigation for polarssl, it is recommended to use TLS 1.1, which is supported in all releases
• tlslite
  [wheezy] - tlslite (Minor issue)
• pound 2.6-2
  Pound 2.6-2 added an anti_beast.patch to mitigate BEAST attacks.
• erlang 1:15.b-dfsg-1
  [squeeze] - erlang (Minor issue)
• asterisk 1:13.7.2dfsg-1
  [jessie] - asterisk 1:11.13.1dfsg-2+deb8u1
  [wheezy] - asterisk (Minor issue)
  [squeeze] - asterisk (Not supported in Squeeze LTS)
  http://downloads.digium.com/pub/security/AST-2016-001.html
  https://issues.asterisk.org/jira/browse/ASTERISK-24972
  patch for 11 (jessie): https://code.asterisk.org/code/changelog/asterisk?cs=f233bcd81d85626ce5bdd27b05bc95d131faf3e4
  all versions vulnerable, backport required for wheezy

It was found that apt-key in apt, all versions, do not correctly validate gpg keys with the master keyring, leading to a potential man-in-the-middle attack.

---

• apt (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642480)
  Not exploitable in Debian, since no keyring URI is defined

A Memory Leak vulnerability exists in SQLite Project SQLite3 3.35.1 and 3.37.0 via maliciously crafted SQL Queries (made via editing the Database File), it is possible to query a record, and leak subsequent bytes of memory that extend beyond the record, which could let a malicious user obtain sensitive information. NOTE: The developer disputes this as a vulnerability stating that If you give SQLite a corrupted database file and submit a query against the database, it might read parts of the database that you did not intend or expect.

---

• sqlite3 (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005974)
• sqlite (unimportant)
  https://github.com/guyinatuxedo/sqlite3_record_leaking
  https://bugzilla.redhat.com/show_bug.cgi?id=2054793
  https://sqlite.org/forum/forumpost/056d557c2f8c452ed5bb9c215414c802b215ce437be82be047726e521342161e
  Negligible security impact

cJSON 1.7.15 might allow a denial of service via a crafted JSON document such as {"a": true, "b": [ null,9999999999999999999999999999999999999999999999912345678901234567]}.

---

• cjson (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103687)
  [bookworm] - cjson (Minor issue)
  [bullseye] - cjson (Minor issue)
  https://github.com/boofish/json_bugs/tree/main/cjson

Buffer Overflow in hiredis 1.2.0 allows a local attacker to cause a denial of service via the sdscatlen function.

---

REJECTED

GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.

---

• gnupg2 (unimportant)
  https://bugzilla.redhat.com/show_bug.cgi?id=2127010
  https://dev.gnupg.org/D556
  https://dev.gnupg.org/T5993
  https://www.openwall.com/lists/oss-security/2022/07/04/8
  GnuPG upstream is not implementing this change.

In GNU Coreutils through 8.29, chown-core.c in chown and chgrp does not prevent replacement of a plain file with a symlink during use of the POSIX "-R -L" options, which allows local users to modify the ownership of arbitrary files by leveraging a race condition.

---

• coreutils (unimportant)
  http://lists.gnu.org/archive/html/coreutils/2017-12/msg00045.html
  https://www.openwall.com/lists/oss-security/2018/01/04/3
  Documentation patches proposed:
  https://lists.gnu.org/archive/html/coreutils/2017-12/msg00072.html
  https://lists.gnu.org/archive/html/coreutils/2017-12/msg00073.html
  Neutralised by kernel hardening

Tar 1.15.1 does not properly warn the user when extracting setuid or setgid files, which may allow local users or remote attackers to gain privileges.

---

This is intended behaviour, after all tar is an archiving tool and you
need to give -p as a command line flag

• tar (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=328228; unimportant)

xmlXIncludeAddNode in xinclude.c in libxml2 before 2.11.0 has a use-after-free.

---

[experimental] - libxml2 2.12.3+dfsg-0exp1

• libxml2 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094238)
  Fixed by: https://gitlab.gnome.org/GNOME/libxml2/-/commit/5a19e21605398cef6a8b1452477a8705cb41562b (v2.11.0)
  UAF DOM\XMLDocument xinclude php/php-src#17467

An issue was discovered in xmllint (from libxml2) before 2.11.8 and 2.12.x before 2.12.7. Formatting error messages with xmllint --htmlout can result in a buffer over-read in xmlHTMLPrintFileContext in xmllint.c.

---

• libxml2 (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071162)
  https://gitlab.gnome.org/GNOME/libxml2/-/issues/720
  Fixed by: https://gitlab.gnome.org/GNOME/libxml2/-/commit/8ddc7f13337c9fe7c6b6e616f404b0fffb8a5145 (v2.11.8)
  Fixed by: https://gitlab.gnome.org/GNOME/libxml2/-/commit/2876ac5392a4e891b81e40e592c3ac6cb46016ce (v2.12.7)
  Crash in CLI tool, no security impact

In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(|)(\1\1)*' in grep, a different issue than CVE-2018-20796. NOTE: the software maintainer disputes that this is a vulnerability because the behavior occurs only with a crafted pattern

---

• glibc (unimportant)
• eglibc (unimportant)
  https://sourceware.org/bugzilla/show_bug.cgi?id=24269

GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may guess the heap addresses of pthread_created thread. The component is: glibc. NOTE: the vendor's position is "ASLR bypass itself is not a vulnerability.

---

• glibc (unimportant)
  Not treated as a security issue by upstream
  https://sourceware.org/bugzilla/show_bug.cgi?id=22853

GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass ASLR using cache of thread stack and heap. The component is: glibc. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.

---

• glibc (unimportant)
  Not treated as a security issue by upstream
  https://sourceware.org/bugzilla/show_bug.cgi?id=22852

GNU Libc current is affected by: Re-mapping current loaded library with malicious ELF file. The impact is: In worst case attacker may evaluate privileges. The component is: libld. The attack vector is: Attacker sends 2 ELF files to victim and asks to run ldd on it. ldd execute code. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.

---

• glibc (unimportant)
  Not treated as a security issue by upstream
  https://sourceware.org/bugzilla/show_bug.cgi?id=22851

GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass stack guard protection. The component is: nptl. The attack vector is: Exploit stack buffer overflow vulnerability and use this bypass vulnerability to bypass stack guard. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.

---

• glibc (unimportant)
  Not treated as a security issue by upstream
  https://sourceware.org/bugzilla/show_bug.cgi?id=22850

In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(\227|)(\1\1|t1|\\2537)+' in grep.

---

• glibc (unimportant)
• eglibc (unimportant)
  https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34141
  https://lists.gnu.org/archive/html/bug-gnulib/2019-01/msg00108.html
  No treated as vulnerability: https://sourceware.org/glibc/wiki/Security%20Exceptions

The glob implementation in the GNU C Library (aka glibc or libc6) allows remote authenticated users to cause a denial of service (CPU and memory consumption) via crafted glob expressions that do not match any pathnames, as demonstrated by glob expressions in STAT commands to an FTP daemon, a different vulnerability than CVE-2010-2632.

---

• glibc (unimportant)
• eglibc (unimportant)
  That's standard POSIX behaviour implemented by (e)glibc. Applications using
  glob need to impose limits for themselves

libldap in certain third-party OpenLDAP packages has a certificate-validation flaw when the third-party package is asserting RFC6125 support. It considers CN even when there is a non-matching subjectAltName (SAN). This is fixed in, for example, openldap-2.4.46-10.el8 in Red Hat Enterprise Linux.

---

• openldap (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965184)
  https://bugs.openldap.org/show_bug.cgi?id=9266
  https://bugzilla.redhat.com/show_bug.cgi?id=1740070
  RedHat/CentOS applied patch: https://git.centos.org/rpms/openldap/raw/67459960064be9d226d57c5f82aaba0929876813/f/SOURCES/openldap-tlso-dont-check-cn-when-bad-san.patch
  OpenLDAP upstream did dispute the issue as beeing valid, as the current libldap
  behaviour does conform with RFC4513. RFC6125 does not superseed the rules for
  verifying service identity provided in specifications for existing application
  protocols published prior to RFC6125, like RFC4513 for LDAP.

contrib/slapd-modules/nops/nops.c in OpenLDAP through 2.4.45, when both the nops module and the memberof overlay are enabled, attempts to free a buffer that was allocated on the stack, which allows remote attackers to cause a denial of service (slapd crash) via a member MODDN operation.

---

• openldap (unimportant)
  http://www.openldap.org/its/index.cgi/Incoming?id=8759
  nops slapd-module not built

slapd in OpenLDAP 2.4.45 and earlier creates a PID file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for PID file modification before a root script executes a "kill cat /pathname" command, as demonstrated by openldap-initscript.

---

• openldap (unimportant)
  http://www.openldap.org/its/index.cgi?findid=8703
  Negligible security impact, but filed #877512

The nss_parse_ciphers function in libraries/libldap/tls_m.c in OpenLDAP does not properly parse OpenSSL-style multi-keyword mode cipher strings, which might cause a weaker than intended cipher to be used and allow remote attackers to have unspecified impact via unknown vectors.

---

• openldap (unimportant)
  Debian builds with GNUTLS, not NSS

An issue was discovered in systemd 253. An attacker can modify the contents of past events in a sealed log file and then adjust the file such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."

---

• systemd (unimportant)
  Disputed by upstream
  https://github.com/kastel-security/Journald/blob/main/journald-publication.pdf

An issue was discovered in systemd 253. An attacker can truncate a sealed log file and then resume log sealing such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."

---

• systemd (unimportant)
  Disputed by upstream
  https://github.com/kastel-security/Journald/blob/main/journald-publication.pdf

An issue was discovered in systemd 253. An attacker can modify a sealed log file such that, in some views, not all existing and sealed log messages are displayed. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."

---

• systemd (unimportant)
  Disputed by upstream
  https://github.com/kastel-security/Journald/blob/main/journald-publication.pdf

systemd, when updating file permissions, allows local users to change the permissions and SELinux security contexts for arbitrary files via a symlink attack on unspecified files.

---

• systemd (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725357)
  [wheezy] - systemd (/etc/tmpfiles.d not supported in Wheezy)
  https://bugzilla.redhat.com/show_bug.cgi?id=859060
  only relevant to systems running systemd along with selinux

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/lib/gssapi/krb5/k5sealv3.c.

---

• krb5 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064965; unimportant)
  https://github.com/LuMingYinDetect/krb5_defects/blob/main/krb5_detect_2.md
  Fixed by: krb5/krb5@c5f9c81
  Codepath cannot be triggered via API calls, negligible security impact
  https://mailman.mit.edu/pipermail/kerberos/2024-March/023095.html

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak in /krb5/src/lib/rpc/pmap_rmt.c.

---

• krb5 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064965; unimportant)
  https://github.com/LuMingYinDetect/krb5_defects/blob/main/krb5_detect_1.md
  Fixed by: krb5/krb5@c5f9c81
  Unused codepath, negligible security impact
  https://mailman.mit.edu/pipermail/kerberos/2024-March/023095.html

An issue was discovered in MIT Kerberos 5 (aka krb5) through 1.16. There is a variable "dbentry->n_key_data" in kadmin/dbutil/dump.c that can store 16-bit data but unknowingly the developer has assigned a "u4" variable to it, which is for 32-bit data. An attacker can use this vulnerability to affect other artifacts of the database as we know that a Kerberos database dump file contains trusted data.

---

• krb5 (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889684)
  https://github.com/poojamnit/Kerberos-V5-1.16-Vulnerabilities/tree/master/Integer%20Overflow
  non-issue, codepath is only run on trusted input, potential integer
  overflow is non-issue

• krb5 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094730)
  https://bugzilla.redhat.com/show_bug.cgi?id=2342796
  Fixed by: krb5/krb5@78ceba0

sqlite3 v3.40.1 was discovered to contain a segmentation violation at /sqlite3_aflpp/shell.c.

---

REJECTED

A Memory Leak vulnerability exists in SQLite Project SQLite3 3.35.1 and 3.37.0 via maliciously crafted SQL Queries (made via editing the Database File), it is possible to query a record, and leak subsequent bytes of memory that extend beyond the record, which could let a malicious user obtain sensitive information. NOTE: The developer disputes this as a vulnerability stating that If you give SQLite a corrupted database file and submit a query against the database, it might read parts of the database that you did not intend or expect.

---

• sqlite3 (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005974)
• sqlite (unimportant)
  https://github.com/guyinatuxedo/sqlite3_record_leaking
  https://bugzilla.redhat.com/show_bug.cgi?id=2054793
  https://sqlite.org/forum/forumpost/056d557c2f8c452ed5bb9c215414c802b215ce437be82be047726e521342161e
  Negligible security impact

HTTP::Tiny before 0.083, a Perl core module since 5.13.9 and available standalone on CPAN, has an insecure default TLS configuration where users must opt in to verify certificates.

---

• libhttp-tiny-perl 0.088-1 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962407; unimportant)
  [experimental] - perl 5.38.0~rc2-1
• perl 5.38.2-2 (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954089)
  https://www.openwall.com/lists/oss-security/2023/04/18/14
  verify_SSL being true by default (redux) chansen/p5-http-tiny#134
  https://blog.hackeriet.no/perl-http-tiny-insecure-tls-default-affects-cpan-modules/
  https://hackeriet.github.io/cpan-http-tiny-overview/
  Applications need to explicitly opt in to enable verification.

_is_safe in the File::Temp module for Perl does not properly handle symlinks.

---

• perl (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776268)
  http://thread.gmane.org/gmane.comp.security.oss.general/6174/focus=6177
  File:Temp::_is_safe() allows unsafe traversal of symlinks [rt.cpan.org #69106] Perl-Toolchain-Gang/File-Temp#14

DISPUTEDA failure in the -fstack-protector feature in GCC-based toolchains that target AArch64 allows an attacker to exploit an existing buffer overflow in dynamically-sized local variables in your application without this being detected. This stack-protector failure only applies to C99-style dynamically-sized local variables or those created using alloca(). The stack-protector operates as intended for statically-sized local variables. The default behavior when the stack-protector detects an overflow is to terminate your application, resulting in controlled loss of availability. An attacker who can exploit a buffer overflow without triggering the stack-protector might be able to change program flow control to cause an uncontrolled loss of availability or to go further and affect confidentiality or integrity. NOTE: The GCC project argues that this is a missed hardening bug and not a vulnerability by itself.

---

• gcc-13 13.2.0-4 (unimportant)
• gcc-12 12.3.0-9 (unimportant)
• gcc-11 11.4.0-4 (unimportant)
• gcc-10 10.5.0-3 (unimportant)
• gcc-9 9.5.0-6 (unimportant)
• gcc-8 (unimportant)
• gcc-7 (unimportant)
  GHSA-x7ch-h5rf-w2mf
  Not considered a security issue by GCC upstream
  https://developer.arm.com/Arm%20Security%20Center/GCC%20Stack%20Protector%20Vulnerability%20AArch64

libiberty/rust-demangle.c in GNU GCC 11.2 allows stack consumption in demangle_const, as demonstrated by nm-new.

---

• gcc-12 (unimportant)
  Negligible security impact
  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105039

Remote packet capture support is disabled by default in libpcap. When a user builds libpcap with remote packet capture support enabled, one of the functions that become available is pcap_findalldevs_ex(). One of the function arguments can be a filesystem path, which normally means a directory with input data files. When the specified path cannot be used as a directory, the function receives NULL from opendir(), but does not check the return value and passes the NULL value to readdir(), which causes a NULL pointer derefence.

---

• libpcap 1.10.5-1 (unimportant)
  the-tcpdump-group/libpcap@0f8a103 (master)
  the-tcpdump-group/libpcap@8a633ee (libpcap-1.10.5)
  Builts in Debian do not enable remote package capture (--enable-remote)

In affected libpcap versions during the setup of a remote packet capture the internal function sock_initaddress() calls getaddrinfo() and possibly freeaddrinfo(), but does not clearly indicate to the caller function whether freeaddrinfo() still remains to be called after the function returns. This makes it possible in some scenarios that both the function and its caller call freeaddrinfo() for the same allocated memory block. A similar problem was reported in Apple libpcap, to which Apple assigned CVE-2023-40400.

---

• libpcap 1.10.5-1 (unimportant)
  the-tcpdump-group/libpcap@262e4f3 (master)
  the-tcpdump-group/libpcap@2aa69b0 (libpcap-1.10.5)
  Builts in Debian do not enable remote package capture (--enable-remote)

In GNU Coreutils through 8.29, chown-core.c in chown and chgrp does not prevent replacement of a plain file with a symlink during use of the POSIX "-R -L" options, which allows local users to modify the ownership of arbitrary files by leveraging a race condition.

---

• coreutils (unimportant)
  http://lists.gnu.org/archive/html/coreutils/2017-12/msg00045.html
  https://www.openwall.com/lists/oss-security/2018/01/04/3
  Documentation patches proposed:
  https://lists.gnu.org/archive/html/coreutils/2017-12/msg00072.html
  https://lists.gnu.org/archive/html/coreutils/2017-12/msg00073.html
  Neutralised by kernel hardening

Tar 1.15.1 does not properly warn the user when extracting setuid or setgid files, which may allow local users or remote attackers to gain privileges.

---

This is intended behaviour, after all tar is an archiving tool and you
need to give -p as a command line flag

• tar (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=328228; unimportant)

GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.

---

• gnupg2 (unimportant)
  https://bugzilla.redhat.com/show_bug.cgi?id=2127010
  https://dev.gnupg.org/D556
  https://dev.gnupg.org/T5993
  https://www.openwall.com/lists/oss-security/2022/07/04/8
  GnuPG upstream is not implementing this change.

It was found that apt-key in apt, all versions, do not correctly validate gpg keys with the master keyring, leading to a potential man-in-the-middle attack.

---

• apt (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642480)
  Not exploitable in Debian, since no keyring URI is defined

initscripts in rPath Linux 1 sets insecure permissions for the /var/log/btmp file, which allows local users to obtain sensitive information regarding authentication attempts. NOTE: because sshd detects the insecure permissions and does not log certain events, this also prevents sshd from logging failed authentication attempts by remote attackers.

---

• shadow (unimportant)
  See #290803, on Debian LOG_UNKFAIL_ENAB in login.defs is set to no so
  unknown usernames are not recorded on login failures

cipher/elgamal.c in Libgcrypt through 1.8.2, when used to encrypt messages directly, improperly encodes plaintexts, which allows attackers to obtain sensitive information by reading ciphertext data (i.e., it does not have semantic security in face of a ciphertext-only attack). The Decisional Diffie-Hellman (DDH) assumption does not hold for Libgcrypt's ElGamal implementation.

---

• libgcrypt20 (unimportant)
• libgcrypt11 (unimportant)
• gnupg1 (unimportant)
• gnupg (unimportant)
  https://github.com/weikengchen/attack-on-libgcrypt-elgamal
  https://github.com/weikengchen/attack-on-libgcrypt-elgamal/wiki
  https://lists.gnupg.org/pipermail/gcrypt-devel/2018-February/004394.html
  GnuPG uses ElGamal in hybrid mode only.
  This is not a vulnerability in libgcrypt, but in an application using
  it in an insecure manner, see also
  https://lists.gnupg.org/pipermail/gcrypt-devel/2018-February/004401.html

libcurl skips the certificate verification for a QUIC connection under certain conditions, when built to use wolfSSL. If told to use an unknown/bad cipher or curve, the error path accidentally skips the verification and returns OK, thus ignoring any certificate problems.

---

• curl 8.7.1-1 (unimportant)
  https://curl.se/docs/CVE-2024-2379.html
  Introduced by: curl/curl@5d044ad (curl-8_6_0)
  Fixed by: curl/curl@aedbbdf (curl-8_7_0)
  curl in Debian not built with wolfSSL support

The SSL protocol, as used in certain configurations in Microsoft Windows and Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Opera, and other products, encrypts data by using CBC mode with chained initialization vectors, which allows man-in-the-middle attackers to obtain plaintext HTTP headers via a blockwise chosen-boundary attack (BCBA) on an HTTPS session, in conjunction with JavaScript code that uses (1) the HTML5 WebSocket API, (2) the Java URLConnection API, or (3) the Silverlight WebClient API, aka a "BEAST" attack.

---

• sun-java6 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645881)
  [lenny] - sun-java6 (Non-free not supported)
  [squeeze] - sun-java6 (Non-free not supported)
• openjdk-6 6b23~pre11-1
• openjdk-7 7~b147-2.0-1
• iceweasel (Vulnerable code not present)
  http://blog.mozilla.com/security/2011/09/27/attack-against-tls-protected-communications/
• chromium-browser 15.0.874.106~r107270-1
  [squeeze] - chromium-browser
• lighttpd 1.4.30-1
  strictly speaking this is no lighttpd issue, but lighttpd adds a workaround
• curl 7.24.0-1
  http://curl.haxx.se/docs/adv_20120124B.html
• python2.6 2.6.8-0.1 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684511)
  [squeeze] - python2.6 (Minor issue)
• python2.7 2.7.3~rc1-1
• python3.1 (bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678998)
  [squeeze] - python3.1 (Minor issue)
• python3.2 3.2.3~rc1-1
  http://bugs.python.org/issue13885
  python3.1 is fixed starting 3.1.5
• cyassl
• gnutls26 (unimportant)
• gnutls28 (unimportant)
  No mitigation for gnutls, it is recommended to use TLS 1.1 or 1.2 which is supported since 2.0.0
• haskell-tls (unimportant)
  No mitigation for haskell-tls, it is recommended to use TLS 1.1, which is supported since 0.2
• matrixssl (low)
  [squeeze] - matrixssl (Minor issue)
  [wheezy] - matrixssl (Minor issue)
  matrixssl fix this upstream in 3.2.2
• bouncycastle 1.49+dfsg-1
  [squeeze] - bouncycastle (Minor issue)
  [wheezy] - bouncycastle (Minor issue)
  No mitigation for bouncycastle, it is recommended to use TLS 1.1, which is supported since 1.4.9
• nss 3.13.1.with.ckbi.1.88-1
  https://bugzilla.mozilla.org/show_bug.cgi?id=665814
  https://hg.mozilla.org/projects/nss/rev/7f7446fcc7ab
• polarssl (unimportant)
  No mitigation for polarssl, it is recommended to use TLS 1.1, which is supported in all releases
• tlslite
  [wheezy] - tlslite (Minor issue)
• pound 2.6-2
  Pound 2.6-2 added an anti_beast.patch to mitigate BEAST attacks.
• erlang 1:15.b-dfsg-1
  [squeeze] - erlang (Minor issue)
• asterisk 1:13.7.2dfsg-1
  [jessie] - asterisk 1:11.13.1dfsg-2+deb8u1
  [wheezy] - asterisk (Minor issue)
  [squeeze] - asterisk (Not supported in Squeeze LTS)
  http://downloads.digium.com/pub/security/AST-2016-001.html
  https://issues.asterisk.org/jira/browse/ASTERISK-24972
  patch for 11 (jessie): https://code.asterisk.org/code/changelog/asterisk?cs=f233bcd81d85626ce5bdd27b05bc95d131faf3e4
  all versions vulnerable, backport required for wheezy

A flaw was found in the util-linux chfn and chsh utilities when compiled with Readline support. The Readline library uses an "INPUTRC" environment variable to get a path to the library config file. When the library cannot parse the specified file, it prints an error message containing data from the file. This flaw allows an unprivileged user to read root-owned files, potentially leading to privilege escalation. This flaw affects util-linux versions prior to 2.37.4.

---

• util-linux (unimportant)
  https://bugzilla.redhat.com/show_bug.cgi?id=2053151
  https://lore.kernel.org/util-linux/[email protected]/T/#u
  util-linux/util-linux@faa5a3a
  util-linux in Debian does build with readline support but chfn and chsh are provided
  by src:shadow and util-linux is configured with --disable-chfn-chsh

GLib 2.31.8 and earlier, when the g_str_hash function is used, computes hash values without restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted input to an application that maintains a hash table. NOTE: this issue may be disputed by the vendor; the existence of the g_str_hash function is not a vulnerability in the library, because callers of g_hash_table_new and g_hash_table_new_full can specify an arbitrary hash function that is appropriate for the application.

---

• glib2.0 (unimportant; bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655044)

OpenSSL 0.9.8i on the Gaisler Research LEON3 SoC on the Xilinx Virtex-II Pro FPGA uses a Fixed Width Exponentiation (FWE) algorithm for certain signature calculations, and does not verify the signature before providing it to a caller, which makes it easier for physically proximate attackers to determine the private key via a modified supply voltage for the microprocessor, related to a "fault-based attack."

---

http://www.eecs.umich.edu/~valeria/research/publications/DATE10RSA.pdf
openssl/openssl#24540
Fault injection based attacks are not within OpenSSLs threat model according
to the security policy: https://www.openssl.org/policies/general/security-policy.html